Traffic offload via local network

ABSTRACT

For traffic offload via a local network, a MME may obtain from a HSS, subscription data including SIPTO related permissions defined on APN basis that indicate SIPTO prohibited, indicate SIPTO allowed excluding SIPTO via Local Network (SIPTO@LN), and/or indicate SIPTO allowed including SIPTO@LN. Then, the MME may obtain information about one or more local Gateways (GWs) capable of offloading selected traffic, such information indicating which of the one or more local GWs provides access to which Packet Data Networks (PDNs), with each PDN being identified by its associated APN. Finally, the MME may process PDN connections and/or PDN disconnections in order to support offloading of the selected traffic. The counterpart UE includes the appropriate means of hardware and/or software that is configured to support and perform SIPTO@LN.

TECHNICAL FIELD

The present invention relates to a method of controlling traffic offload via local network

BACKGROUND ART

In the related art, traffic offload via a local network techniques were not adequate. As such, the related art technologies do not sufficiently address such issues, and thus do not offer appropriate solutions.

DISCLOSURE OF INVENTION Solution to Problem

The present inventors recognized at least the above-identified drawbacks of the related art. Based upon such recognition, the various features described hereafter have been conceived such that certain procedures related to traffic offload via local network techniques are more efficiently and effectively performed. In particular, particular techniques and concepts to support Selected IP Traffic Offload (SIPTO) at a local network have been conceived and implemented. As a result, service continuity for selected IP traffic offload can be achieved.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 shows some exemplary concepts related to Internet access from macro cell vs. Internet access from Femto cell (before and after performing SIPTO@LN) for the invention embodiments.

FIGS. 2 a and 2 b show a table containing exemplary information storage in the HSS for the invention embodiments.

FIG. 3 shows some exemplary concepts related to a call flow illustrating the impacted S1-AP messages for the invention embodiments.

FIG. 4 shows some exemplary call flows for E-UTRAN Initial Attach and UE requested PDN connectivity procedures for the invention embodiments.

FIG. 5 depicts an exemplary signal flow for UE requested PDN connectivity procedures for the invention embodiments.

FIG. 6 shows an exemplary MME that can be used to implement the invention embodiments.

MODE FOR THE INVENTION

The inventive concepts and features herein are generally explained in terms of 3GPP Universal Mobile Telecommunication System (UMTS)/Evolved Packet System (EPS) technology. However, such details are not meant to limit the various features described herein, which are applicable to other types of mobile and/or wireless (radio) communication systems and methods.

Hereafter, some aspects about (cellular) traffic offload via a Local Network residing on customer premises will be described.

Selected IP Traffic Offload (SIPTO) is a 3GPP Release 10 (Rel-10) feature allowing the operator to offload user's traffic by selecting a Packet Data Gateway (PGW) residing close to the Evolved Packet Core (EPC) network edge.

Local IP Access (LIPA) is a 3GPP Rel-10 feature providing access to resources on the Local Network (LN) (i.e. the network located inside the customer's home or enterprise premises) via a Femto cell (a.k.a. Home (e)NodeB).

In 3GPP Rel-11 there is an ongoing work item referred to as LIMONET (see TR 23.859) aiming at enhancing the LIPA and SIPTO features.

Specifically related to SIPTO enhancements, the Rel-11 work item aims at defining a solution that would allow the operator to offload user's traffic on the Local Network (LN) inside the customer premises. This type of offload is shortly referred to as SIPTO@LN.

In contrast to Rel-10 LIPA, whose aim is to provide access to resources on the local network itself, the Rel-11 SIPTO@LN feature aims at providing access to external networks (e.g. the Internet) via the local network (the underlying assumption being that the Local Network eventually has connectivity towards the desired external network).

In comparison to Rel-10 SIPTO, the Rel-11 SIPTO@LN feature may impact the user experience, given that the Local Network may not have some functionality that is present in the operator's EPC network (e.g. parental control, website accelerators, compression engines, etc). Acknowledging that this potential change in user experience before and after offload may not be acceptable to all users, there is a requirement that the network should be able to seek user's consent before offloading the traffic, based on operator policies.

This invention disclosure proposes several architecture enablers in order to address the requirements of the Rel-11 SIPTO@LN feature. Namely, it is proposed to enhance the user's subscription information in the HSS, as well as to enhance the signalling capability of the Home (e)NodeB subsystem on the S1/Iu interface.

FIG. 1 shows Internet access from macro cell vs. Internet access from Femto cell (before and after performing SIPTO@LN).

Namely, FIG. 1 shows a scenario where the UE 501 can access the Internet 570 in three different ways:

First, when the user is outside his home and connected to a macro cell 510, the UE 501 establishes a PDN connection (PDN1) associated with the APN that is used for access to the Internet (e.g. APN=“Internet”). The network may decide to SIPTO this PDN connection by requesting a disconnection+reconnection (a Rel-10 mechanism) and selecting a PGW that is closer to the network edge upon PDN reconnection.

Second, when the user enters his home, the PDN connection (PDN1) is handed over to the home Femto cell 540. As previously, the network may again decide to SIPTO this PDN connection by requesting a disconnection+reconnection in order to select a PGW that is closer to the network edge, nevertheless, the PGW still remains located inside the EPC 520.

Third, if the network knows that the Local Gateway (L-GW) 555 residing on the customer premises (home network 550) has unrestricted connectivity to the Internet (e.g. by relying on the Internet Service Provider's backhaul network 560), it may decide to trigger disconnection +reconnection, and this time select the L-GW upon reconnection (instead of selecting a PGW residing in the EPC 520). Such a PDN connection is referred to as PDN2 in FIG. 1.

The third case described above (i.e. access to the Internet via the Local Gateway) is actually a perfect use case example for the Rel-11 SIPTO@LN feature, in that, based on network's initiative, the user's Internet-bound traffic is offloaded via the Local Network.

As mentioned in the introduction, SIPTO@LN may require user's consent due to the possible service alteration subsequent to offload. This consent may be part of the subscription information, but it may also involve a real-time interaction with the user, depending on operator's policies and the terminal capabilities.

The embodiments of this disclosure address the scenario described for the case where the user's Internet-bound traffic is offloaded via the Local Network (i.e. via a Local Gateway).

Embodiments of this invention propose two enablers for SIPTO@LN:

Enhancement to the user's subscription information in the HSS by enhancing the SIPTO Permissions flag associated to a specific Access Point Name (APN);

Enhancement to the S1-AP signalling indicating whether the Local Gateway (L-GW) is capable for traffic offload via the Local Network.

FIGS. 2 a-2 b show a table of exemplary information storage in the HSS. As seen from the table, each PDN subscription context currently contains a SIPTO Permissions flag associated to it. This flag contains binary information indicating whether the traffic associated with this APN is allowed or prohibited for SIPTO.

As previously explained, with Rel-11 SIPTO@LN the user experience before and after offload may not be the same, due to possible lack of parental control, etc. for the traffic offloaded on the Local Network, which may not be acceptable to some users.

It is therefore proposed to enhance the SIPTO Permissions flag so that for traffic that is authorized for Rel-10 SIPTO, it is in addition indicated whether it is also authorized for Rel-11 SIPTO@LN.

Only if the traffic associated to a specific APN is authorized for SIPTO@LN will the EPC network attempt to offload such traffic via the Local Network. Note that the decision for offloading may or may not involve a real-time interaction with the user, depending on the operator's policies and terminal capabilities. The real-time interaction can be performed by using specific the NAS signaling messages.

The following table shows an example of the [S1-AP] UPLINK NAS TRANSPORT message content.

IE type and Semantics Assigned IE/Group Name Presence Range reference description Criticality Criticality Message Type M 9.2.1.1 YES ignore MME UE S1AP ID M 9.2.3.3 YES reject eNB UE S1AP ID M 9.2.3.4 YES reject NAS-PDU M 9.2.3.5 YES reject E-UTRAN CGI M 9.2.1.38 YES ignore TAI M 9.2.3.16 YES ignore GW Transport O Transport Indicating YES ignore Layer Address Layer Address GW Transport 9.2.2.1 Layer Address if the GW is collocated with eNB

This message and some other S1-AP protocol messages are used in Rel-10 specifications for conveying the L-GW address on the S5 reference point termination for the Local Gateway that is used for LIPA.

In order to enable the SIPTO@LN feature, it is proposed to enhance this information so that it indicates whether the L-GW has the capability to provide offload for selected traffic (i.e. whether it has connectivity to the packet data network which serves as the destination for the offloaded traffic):

This signaled information can be APN-specific if the L-GW has the capability for offloading traffic associated with specific APNs only;

Given that the most likely candidate for offload is traffic bound to the Internet, the L-GW may have a special (non-APN specific) indication that it is capable for offloading of Internet traffic, without having to signal this as APN-specific information. In this case the underlying assumption is that the MME knows which APNs are used to provide access to the Internet.

It should be noted that the Local Gateway used for LIPA may be different from the Local Gateway used for SIPTO@LN, in which case the information for these two is signalled separately in the S1-AP messages.

The solution description in this disclosure is made for the E-UTRAN case (i.e. HeNB), but can be adapted in straight-forward manner to the case where UTRAN (i.e. HNB) connects to the Evolved Packet Core (EPC).

FIG. 3 shows an example call flow illustrating the impacted S1-AP messages. The depicted example of the UE triggered Service Request procedure that may comprise the following steps:

1. It is assumed that the UE 710 with established PDN connection(s) has moved from a macro cell to a Femto cell in Idle mode.

2. UE wishes to move to Connected mode by invoking the Service Request procedure by sending a NAS Service Request message to the eNodeB 720.

3. The [NAS] Service Request message is transparently conveyed from the eNodeB 720 to the MME 730 in the [S1-AP] UPLINK NAS TRANSPORT message. Also piggybacked on this message is information on Local Gateway that is capable of offloading traffic, either for specific APN(s) or for Internet traffic. The MME 730 stores this information.

4. Completion of the Service Request procedure.

5. Based on the information received in step 2, and provided that the SIPTO permission flag in the UE context allows for SIPTO@LN for this specific APN, the MME 730 initiates the SIPTO procedure i.e. PDN disconnection with a cause “Reconnection required”.

6. When the UE requests PDN reconnection, the MME 730 selects the L-GW 760.

A similar call flow can be drawn for the handover scenario i.e. when a UE with established PDN connection is handed over from a macro cell to a Femto cell. In this case the information on SIPTO@LN support is carried over S1-MME inside the [S1-AP] Handover Request Acknowledge message, [S1-AP] Handover Notify message or [S1-AP] Path Switch Request message. The message choice depends on the type of handover (S1-based vs. X2-based) and the urgency of providing the information for SIPTO@LN support to the MME.

For the case where the UE attaches from the Femto cell, the impacted message is [S1-AP] UE Initial Message.

In reference to FIG. 4 (that depicts E-UTRAN Initial Attach), the impacted step is step 2. If the eNodeB supports SIPTO@LN, it includes information about the L-GW(s) residing in the local network that are capable for selective traffic offload in the Initial UE message to the MME (e.g. L-GW address and supported APN(s) or a non-APN specific indication for offload of Internet traffic).

It should be noted that FIG. 4 depicts some signal flows as solid arrows to indicate that such are necessary, while other signal flows are shown as dotted arrows to denote that such may or may not always need to be performed.

The UE 810 sends an Attach Request message to the eNodeB 820, which delivers such message to the new MME 830 (steps 1 and 2). The new MME 830 cooperates with the old MME/SGSN 840 to send an Identification Request message and receive an Identification Response message (step 3). Then, the new MME 830 sends an Identity Request message to the UE 810, which responds with an Identity Response message (step 4). As a result, an Authentication/Security procedure is performed between the UE 810, the new MME 830 and the HSS 880 (step 5 a). Further, the new MME 830 performs an Identity Request/Response procedure with the UE 810 and performs an ME Identity Check procedure with the EIR 890 (step 5 b). Then, the new MME 830 sends a Ciphered Options Request message to the UE 810, which responds with a Ciphered Options Response message (step 6).

Thereafter, the new MME 830 cooperates with various network entities for session deletion (procedure (E)). Namely, the new MME 830 sends a Delete Session Request message to the PDN GW 860 via the Serving GW 850, and receives a Delete Session Response message from the PDN GW 860 via the Serving GW 850 (step 7). Additionally, the PDN GW 860 cooperates with the PCRF 870 to perform a PCEF Initiated IP-CAN Session Termination procedure (shown as part of procedure (A)).

In step 8, an Update Location Request message is sent by the new MME 830 to the HSS 880, which performs a cancel location procedure with the old MME/SGSN 840 by exchanging a Cancel Location (request) message and a Cancel Location ACK message (step 9).

Then, the old MME/SGSN 840 cooperates with various network entities for session deletion (procedure (F)), which is similar to the session deletion procedure (E). Namely, the old MME/SGSN 840 sends a Delete Session Request message to the PDN GW 860 via the Serving GW 850, and receives a Delete Session Response message from the PDN GW 860 via the Serving GW 850 (step 10). Additionally, the PDN GW 860 cooperates with the PCRF 870 to perform a PCEF Initiated IP-CAN Session Termination procedure (shown as part of procedure (B)).

Thereafter, the HSS 880 sends an Update Location ACK message to the new MME 830 (step 11), and in response, the new MME 830 sends a Create Session Request message to the Serving GW 850 (step 12). As a result, the Serving GW 850 sends a Create Session Request message to the PDN GW 860, which cooperates with the PCRF 870 to perform a PCEF Initiated IP-CAN Session Establishment/Modification procedure, and the PDN GW 860 sends a Create Session Response message back to the Serving GW 850 (procedure (C): steps 13 through 15).

Then, the PDN GW 860 can send First Downlink Data (if not handover) to the

Serving GW 850. In step 16, the Serving GW 850 sends a Create Session Response message to the new MME 830, which then sends an Initial Context Setup Request/Attach Accept message to the eNodeB 820 (step 17). The eNodeB 820 then sends an RRC Connection Reconfiguration message to the UE 810, which responds with an RRC Connection Reconfiguration Complete message, which in turn allows that eNodeB 820 to send an Initial Context Setup Response message to the new MME 830 (steps 18 through 20).

Thereafter, the UE 810 performs a Direct Transfer procedure to the eNodeB 820, which then sends an Attach Complete message to the new MME 830 (steps 21 and 22). Here, First Uplink Data may be sent from the UE 810 to the Serving GW 850, which can then deliver such to the PDN GW 860. Then, the new MME 830 sends a Modify Bearer Request message to the Serving GW 850 (step 23), which can then perform a Modify Bearer Request/Response procedure with the PDN GW 860 (steps 23 a and 23 b of procedure (D)), and respond to the new MME 830 by sending a Modify Bearer Response message back thereto (step 24).

Finally, First Downlink Data can be sent from the PDN GW 860 to the UE 810 via the Serving GW 850, and the new MME 830 can send a Notify Request message to the HSS 880, which can respond with a Notify Response message back to the new MME 830 (steps 25 and 26).

In reference to FIG. 5 (UE requested PDN connectivity procedure) the impacted step is step 1. If the HeNB supports SIPTO@LN, it includes information about the L-GW(s) residing in the local network that are capable for selective traffic offload in the Uplink NAS transport message to the MME (e.g. L-GW address and supported APN(s) or a non-APN specific indication for offload of Internet traffic).

It should be noted that FIG. 5 depicts some signal flows as solid arrows to indicate that such are necessary, while other signal flows are shown as dotted arrows to denote that such may or may not always need to be performed.

The UE 910 sends a PDN Connectivity Request message to the MME 930 (step 1), which then delivers a Create Session Request message to the Serving GW 940 (step 2). Then, procedure (A) is performed among the Serving GW 940, the PDN GW 950, and the PCRF 960. Namely, the Serving GW 940 sends a Create Session Request message to the PDN GW 950 (step 3), which cooperates with the PCRF 960 to performs an IP-CAN Establishment/Modification procedure. Then, the PDN GW 950 sends a Create Session Response message back to the Serving GW 940. Here, First Downlink Data may be send from the PDN GW 950 to the Serving GW 940.

Then, the Serving GW 940 sends a Create Session Response message to the MME 930 (step 6), which then sends a Bearer Setup Request/PDN Connectivity Accept message to the eNodeB 920 (step 7). As a result, the eNodeB 920 sends an RRC Connection Reconfiguration message to the UE 910, which responds with an RRC Connection Reconfiguration Complete message sent back to the eNodeB 920 (steps 8 and 9).

Thereafter, the eNodeB 920 sends a Bearer Setup Response message to the MME 930 (step 10), the UE 910 then performs Direct Transfer to the eNodeB 920 (step 11), and the eNodeB 920 sends a PDN Connectivity Complete message to the MME 930 (step 12). Here, the UE 910 can also send First Uplink Data to the PDN GW via the Serving GW.

Accordingly, the MME 930 sends a Modify Bearer Request message to the Serving GW 940 (step 13), which cooperates with the PDN GW 950 to perform a Modify Bearer Request/Response procedure (steps 13 a and 13 b in procedure (B)). As a result, the Serving GW 940 sends a Modify Bearer Response message back to the MME 930 (step 14). Here, the PDN GW 950 can sends First Downlink Data to the UE 910 via the Serving GW 940.

Finally, the MME 930 can send a Notify Request message to the HSS 970, which can respond with a Notify Response message send back to the MME 930 (steps 15 and 16).

In summary, the embodiments of the invention provide a method comprising: obtaining, by a Mobility Management Entity (MME) from a Home Subscriber Server (HSS), subscription data including Selected IP Traffic Offload (SIPTO) related permissions defined on Access Point Name (APN) basis that indicate at least one among situations comprising SIPTO prohibited, SIPTO allowed excluding SIPTO via Local Network (SIPTO@LN), and SIPTO allowed including SIPTO@LN; receiving, by the MME, information about one or more local Gateways (GWs) capable of offloading selected traffic, said information indicating which of the one or more local GWs provide access to which Packet Data Networks (PDNs), with each PDN being identified by its associated APN; and processing, by the MME, PDN connections and/or PDN disconnections in order to support said offloading of said selected traffic.

The processing step may comprise: performing, by the MME with a User Equipment (UE), a PDN disconnection with request for subsequent reconnection; and when the UE attempts reconnection, selecting, by the MME, one of the local GWs based on the obtained subscription data and the received information about the one or more local GWs. Alternatively, the processing step may comprise: based on a decision by the MME to perform SIPTO@LN for said PDN connections, initiating deactivation, by the MME, of said PDN connections by sending to the UE a Deactivate Bearer Request message indicating that reactivation is required for said PDN connections; and when the UE attempts reactivation, selecting, by the MME, one of the local GWs based on the obtained subscription data and the received information about the one or more local GWs.

It should be noted that if all PDN connections of the UE need to be SIPTO-ed, detaching the UE by the MME with indication reattach requested, denotes that a cause value (such as “explicit detach with reattach required”) is included in DetachRequest message.

The “SIPTO allowed including SIPTO@LN” permission may include implicit user consent or explicit user consent. A single local GW can have multiple APNs. One or more local GWs may be reachable by a Home eNodeB (eNB). A same local GW may support both SIPTO and Local IP Access (LIPA). Also, APN information may be received by the MME from a Home eNB, that provides a list of GWs. If APN information is not received from the Home eNB, then the MME is assumed to know which APNs are used to provide access to the Internet.

It should be noted that, through use of a S1-AP protocol Uplink NAS Transport message, indication about the local GWs providing access to external packet data networks associated with specific APNs can be provided. For a more common case, only a flag that indicates “Internet” may be needed (i.e. the MME needs to know the APN for Internet: operator may configure MME). Also, the GW for SIPTO@LN can be the same as the GW for LIPA. Additionally, SIPTO@LN is performed, if the HSS data and the information about local GWs allows for SIPTO@LN.

Additionally, as shown in FIG. 6, embodiments of the invention provide a Mobility Management Entity (MME) comprising: means for obtaining, from a Home Subscriber Server (HSS), subscription data including Selected IP Traffic Offload (SIPTO) related permissions defined on Access Point Name (APN) basis that indicate at least one among situations comprising SIPTO prohibited, SIPTO allowed excluding SIPTO via Local Network (SIPTO@LN), and SIPTO allowed including SIPTO@LN; means for receiving information about one or more local Gateways (GWs) capable of offloading selected traffic, said information indicating which of the one or more local GWs provide access to which Packet Data Networks (PDNs), with each PDN being identified by its associated APN; and means for processing PDN connections and/or PDN disconnections in order to support said offloading of said selected traffic. Such means (1001) for obtaining, means (1003) for receiving, and means (1005) for processing could be implemented as individual hardware components within the MME 1000. Alternatively, at least one of such means could be implemented as software stored in memory 1002 (or some other storage device) and executable by a processor or controller 1004. Cooperation with various network entities such as the HSS, local gateways, etc. can be performed by sending and receiving signals and information via a transceiver 1006 under the control of the processor/controller 1004.

INDUSTRIAL APPLICABILITY

The features and concepts herein are applicable to and can be implemented in various types of user devices (e.g., mobile terminals, handsets, wireless communication devices, etc.) and/or network devices, entities, components, etc. that can be configured to support the particular traffic offload via a local network techniques described herein.

As the various concepts and features described herein may be embodied in several forms without departing from the characteristics thereof, it should also be understood that the above-described embodiments are not limited by any of the details of the foregoing description, unless otherwise specified, but rather should be construed broadly within its scope as defined in the appended claims. Therefore, all changes and modifications that fall within such scope or equivalents thereof are therefore intended to be embraced by the appended claims. 

1. A method comprising: obtaining, by a Mobility Management Entity (MME) from a Home Subscriber Server (HSS), subscription data including Selected IP Traffic Offload (SIPTO) related permissions defined on Access Point Name (APN) basis that indicate at least one among situations comprising SIPTO prohibited, SIPTO allowed excluding SIPTO via Local Network (SIPTO@LN), and SIPTO allowed including SIPTO@LN; receiving, by the MME, information about one or more local Gateways (GWs) capable of offloading selected traffic, said information indicating which of the one or more local GWs provide access to which Packet Data Networks (PDNs), with each PDN being identified by its associated APN; and processing, by the MME, PDN connections and/or PDN disconnections in order to support said offloading of said selected traffic.
 2. The method of claim 1, wherein the processing step comprises: performing, by the MME with a User Equipment (UE), a PDN disconnection with request for subsequent reconnection; and when the UE attempts reconnection, selecting, by the MME, one of the local GWs based on the obtained subscription data and the received information about the one or more local GWs.
 3. The method of claim 1, wherein the processing step comprises: based on a decision by the MME to perform SIPTO@LN for said PDN connections, initiating deactivation, by the MME, of said PDN connections by sending to the UE a Deactivate Bearer Request message indicating that reactivation is required for said PDN connections; and when the UE attempts reactivation, selecting, by the MME, one of the local GWs based on the obtained subscription data and the received information about the one or more local GWs.
 4. The method of claim 1, wherein the SIPTO allowed including SIPTO@LN includes implicit user consent or explicit user consent.
 5. The method of claim 1, wherein a single local GW supports multiple APNs.
 6. The method of claim 1, wherein one or more local GWs are reachable by a Home eNodeB (eNB).
 7. The method of claim 1, wherein a same local GW supports both SIPTO and Local IP Access (LIPA).
 8. The method of claim 1, wherein APN information is received, by the MME from a Home eNB, that provides a list of GWs.
 9. The method of claim 8, wherein if the APN information is not received from the Home eNB, then the MME is assumed to know which APNs are used to provide access to the Internet.
 10. A Mobility Management Entity (MME) comprising: means for obtaining, from a Home Subscriber Server (HSS), subscription data including Selected IP Traffic Offload (SIPTO) related permissions defined on Access Point Name (APN) basis that indicate at least one among situations comprising SIPTO prohibited, SIPTO allowed excluding SIPTO via Local Network (SIPTO@LN), and SIPTO allowed including SIPTO@LN; means for receiving information about one or more local Gateways (GWs) capable of offloading selected traffic, said information indicating which of the one or more local GWs provide access to which Packet Data Networks (PDNs), with each PDN being identified by its associated APN; and means for processing PDN connections and/or PDN disconnections in order to support said offloading of said selected traffic. 